Skip to content

Conversation

@fayi-da
Copy link
Contributor

@fayi-da fayi-da commented Jun 6, 2025

Making the type more specific to potentially fix the retry

Pull Request Checklist

Cluster Testing

  • If a cluster test is required, comment /cluster_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • If a hard-migration test is required (from the latest release), comment /hdm_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.

PR Guidelines

  • Include any change that might be observable by our partners or affect their deployment in the release notes.
  • Specify fixed issues with Fixes #n, and mention issues worked on using #n
  • Include a screenshot for frontend-related PRs - see README or use your favorite screenshot tool

Merge Guidelines

  • Make the git commit message look sensible when squash-merging on GitHub (most likely: just copy your PR description).

@fayi-da fayi-da force-pushed the fayi/json-api-type-fix branch from ed42dc5 to 18555dc Compare June 6, 2025 09:52
@fayi-da fayi-da requested a review from martinflorian-da June 6, 2025 09:52
Making the type more specific to potentially fix the retry

Signed-off-by: fayi-da <fayimora.femibalogun@digitalasset.com>
@fayi-da fayi-da force-pushed the fayi/json-api-type-fix branch from 18555dc to abc2d9f Compare June 6, 2025 10:23
Copy link
Contributor

@martinflorian-da martinflorian-da left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm probably missing something obvious again, but how will a more narrow retry condition make us retry more often?

@fayi-da
Copy link
Contributor Author

fayi-da commented Jun 6, 2025

Re-posting my comment from the issue


The json returned is:

{
    "status": 400,
    "statusText": "",
    "body": {
        "error": "{\"code\":\"NOT_CONNECTED_TO_ANY_SYNCHRONIZER\",\"cause\":\"This participant is not connected to any synchronizer.\",\"correlationId\":null,\"traceId\":\"68f57a379f608a16d1af4f493b68d56d\",\"context\":{\"participant\":\"participant\",\"definite_answer\":\"false\",\"tid\":\"68f57a379f608a16d1af4f493b68d56d\",\"category\":\"9\"},\"resources\":[],\"errorCategory\":9,\"grpcCodeValue\":9,\"retryInfo\":null,\"definiteAnswer\":null}"
    },
    "name": "JsonApiError"
}

and i can see that body.error contains NOT_CONNECTED_TO_ANY_SYNCHRONIZER which is what we check for here. Might add some extra logging here to get some more info. Potentially the content of error goes from string to json? 🤷

@fayi-da
Copy link
Contributor Author

fayi-da commented Jun 6, 2025

Ignore this PR. I'll probably still keep the types but i've seen what the issue is now :)

@fayi-da fayi-da closed this Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants